-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Roles] Use Query Roles API for Role Management grid screen #194630
base: main
Are you sure you want to change the base?
[Roles] Use Query Roles API for Role Management grid screen #194630
Conversation
…ks to reduce complexity
@elasticmachine merge upstream |
@elasticmachine merge upstream |
…t --include-path /api/status --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/fleet --include-path /api/dashboards --update'
Pinging @elastic/kibana-security (Team:Security) |
logger, | ||
buildFlavor, | ||
}: RouteDefinitionParams) { | ||
router.post( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: Should this be switched to use the versioned router? I see many of the other routes in this directory use it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooh, good point! What makes us choose versioned router vs regular router when building these routes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking for guidance. Ill have some feedback soon
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok so I have the following: For public routes, we will always want to use the versioned router. Otherwise, it's still strongly preferred, but not mandatory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thank you! Updated to versioned router in 989120f
x-pack/plugins/security/server/routes/authorization/roles/query.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/security/server/routes/authorization/roles/query.test.ts
Outdated
Show resolved
Hide resolved
7b84a2b
to
1c542ce
Compare
x-pack/platform/plugins/shared/security/server/routes/authorization/roles/query.test.ts
Outdated
Show resolved
Hide resolved
@elasticmachine merge upstream |
…t --include-path /api/status --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/fleet --include-path /api/dashboards --update'
x-pack/platform/plugins/shared/security/server/routes/authorization/roles/get_all_by_space.ts
Show resolved
Hide resolved
Thank you for the review @kc13greiner! Answered the questions:
Since we're using the wildcard query on the name field, i think it defaults to case sensitivity. Happy to change it to Case insensitive search, what do you think?
I believe the field is not sortable on the API. I've changed the column config in 31cf053 |
This could be a good question for product @bitzandeb !
++ makes sense - thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - works great, very excited for this 🚀
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Async chunks
Page load bundle
History
|
Closes #186266
Release notes
Enhanced Role management to manage larger number of roles by adding server side filtering, pagination and querying.
Summary
Run locally
Start ES with the JVM option to enable this feature:
Start Kibana normally
Navigate to Stack Management > Roles and verify the same behavior as the screen recording below
Screen recording
Screen.Recording.2024-12-23.at.19.46.42.mov
Technical notes
roles/_query
Checklist
Delete any items that are not applicable to this PR.